secure_storage: fix obj_id memory leak #139
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
jforissier
approved these changes
Oct 6, 2025
etienne-lms
approved these changes
Oct 6, 2025
etienne-lms
approved these changes
Oct 6, 2025
|
@quintusfelix, could you update your commit adding the 2 provided review tags in its commit message body? |
Call TEE_Free on obj_id pointer after the object id is copied into the object. Signed-off-by: Boerje Sewing <[email protected]> Reviewed-by: Etienne Carriere <[email protected]> Reviewed-by: Jerome Forissier <[email protected]>
quintusfelix
force-pushed
the
fix_secure_storage_mem_leak
branch
from
fbb9b47 to
974f961
Compare
Done! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Call TEE_Free on obj_id pointer after the object id is copied into the object.